Charging iot devices

ABSTRACT

Methods, apparatuses, and computer-readable medium for charging IoT devices are provided. An example method may include transmitting, to a user equipment (UE), a charging request to charge the IoT device. The example method may further include receiving, from the UE, a fulfillment or a denial associated with the charging request. The example method may further include broadcasting information related to the charging request after receiving the fulfillment or the denial associated with the charging request.

TECHNICAL FIELD

The present disclosure relates generally to communication systems, and more particularly, to wireless communication systems with user equipment (UE) charging Internet of Things (IoT) devices.

INTRODUCTION

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

BRIEF SUMMARY

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus at an IoT device are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to transmit, to a UE, a charging request to charge the IoT device. The memory and the at least one processor coupled to the memory may be further configured to receive, from the UE, a fulfillment or a denial associated with the charging request. The memory and the at least one processor coupled to the memory may be further configured to broadcast information related to the charging request after receiving the fulfillment or the denial associated with the charging request.

In another aspect of the disclosure, a method, a computer-readable medium, and an apparatus at a UE device are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to receive, from an IoT device, a charging request to charge the IoT device. The memory and the at least one processor coupled to the memory may be further configured to transmit, to the IoT device, a fulfillment or a denial associated with the charging request. The memory and the at least one processor coupled to the memory may be further configured to receive, from the IoT device, a broadcast including information related to the charging request after transmitting the fulfillment or the denial associated with the charging request.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.

FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.

FIG. 2B is a diagram illustrating an example of DL channels within a subframe, in accordance with various aspects of the present disclosure.

FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.

FIG. 2D is a diagram illustrating an example of UL channels within a subframe, in accordance with various aspects of the present disclosure.

FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

FIG. 4 is a diagram illustrating example energy harvesting.

FIG. 5 is a diagram illustrating example energy harvesting.

FIG. 6 is a diagram illustrating example energy harvesting.

FIG. 7 is a diagram illustrating an example communication flow between an IoT device and a charging UE.

FIG. 8 is a flowchart of a method of wireless communication.

FIG. 9 is a flowchart of a method of wireless communication.

FIG. 10 is a diagram illustrating an example of a hardware implementation for an example apparatus.

FIG. 11 is a diagram illustrating an example of a hardware implementation for an example apparatus.

DETAILED DESCRIPTION

The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

While aspects and implementations are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases may come about in many different arrangements and scenarios. Innovations described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, implementations and/or uses may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations may occur. Implementations may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders/summers, etc.). It is intended that innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100. The wireless communications system (also referred to as a wireless wide area network (WWAN)) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G Core (5GC)). The base stations 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station). The macrocells include base stations. The small cells include femtocells, picocells, and microcells.

The base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 through first backhaul links 132 (e.g., S1 interface). The base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network 190 through second backhaul links 184. In addition to other functions, the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over third backhaul links 134 (e.g., X2 interface). The first backhaul links 132, the second backhaul links 184, and the third backhaul links 134 may be wired or wireless.

The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102′ may have a coverage area 110′ that overlaps the coverage area 110 of one or more macro base stations 102. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations 102/UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell).

Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communications systems, such as for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

The wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the STAs 152/AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

The small cell 102′ may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102′ may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz, or the like) as used by the Wi-Fi AP 150. The small cell 102′, employing NR in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.

The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz-24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz), and FR5 (114.25 GHz-300 GHz). Each of these higher frequency bands falls within the EHF band.

With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and/or FR5, or may be within the EHF band.

A base station 102, whether a small cell 102′ or a large cell (e.g., macro base station), may include and/or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave frequencies, and/or near millimeter wave frequencies in communication with the UE 104. When the gNB 180 operates in millimeter wave or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may utilize beamforming 182 with the UE 104 to compensate for the path loss and short range. The base station 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate the beamforming.

The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 182′. The UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 182″. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 180/UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 180/UE 104. The transmit and receive directions for the base station 180 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176. The IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service, and/or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

The core network 190 may include an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the AMF 192 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switch (PS) Streaming (PSS) Service, and/or other IP services.

The base station may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit reception point (TRP), or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for a UE 104. Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and/or individually access the network. In some aspects, the UE 104 may be an IoT device or a charging UE.

Referring again to FIG. 1 , in some aspects, the UE 104 may include a charging component 198. In some aspects, the charging component 198 may be configured to transmit, to a UE, a charging request to charge the IoT device. In some aspects, the charging component 198 may be further configured to receive, from the UE, a fulfillment or a denial associated with the charging request. In some aspects, the charging component 198 may be further configured to broadcast information related to the charging request after receiving the fulfillment or the denial associated with the charging request.

In some aspects, the UE 104 may include a charging component 199. In some aspects, the charging component 199 may be configured to receive, from an IoT device, a charging request to charge the IoT device. In some aspects, the charging component 199 may be further configured to transmit, to the IoT device, a fulfillment or a denial associated with the charging request. In some aspects, the charging component 199 may be further configured to receive, from the IoT device, a broadcast including information related to the charging request after transmitting the fulfillment or the denial associated with the charging request.

Although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by FIGS. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL), where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe 3 being configured with slot format 1 (with all UL). While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI), or semi-statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI). Note that the description infra applies also to a 5G NR frame structure that is TDD.

FIGS. 2A-2D illustrate a frame structure, and the aspects of the present disclosure may be applicable to other wireless communication technologies, which may have a different frame structure and/or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols. The symbols on DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also referred to as single carrier frequency-division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to a single stream transmission). The number of slots within a subframe is based on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) and, effectively, the symbol length/duration, which is equal to 1/SCS.

SCS μ Δf = 2^(μ) · 15[kHz] Cyclic prefix 0 15 Normal 1 30 Normal 2 60 Normal, Extended 3 120 Normal 4 240 Normal

For normal CP (14 symbols/slot), different numerologies μ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology μ, there are 14 symbols/slot and 2^(μ) slots/subframe. The subcarrier spacing may be equal to 2^(μ)*15 kHz, where μ is the numerology 0 to 4. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing. FIGS. 2A-2D provide an example of normal CP with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a particular numerology and CP (normal or extended).

A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

As illustrated in FIG. 2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

FIG. 2B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET). A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the DM-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form a synchronization signal (SS)/PBCH block (also referred to as SS block (SSB)). The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs), and paging messages.

As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS). The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK and/or negative ACK (NACK)). The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and/or UCI.

FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller/processor 375. The controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318 TX. Each transmitter 318 TX may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.

At the UE 350, each receiver 354 RX receives a signal through its respective antenna 352. Each receiver 354 RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.

The controller/processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with the DL transmission by the base station 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.

The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

The controller/processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 350. IP packets from the controller/processor 375 may be provided to the EPC 160. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with charging component 198/199 of FIG. 1 .

Energy harvesting is a process where energy is obtained from external sources, such as solar power, thermal energy, kinetic energy, ambient energy, salinity gradients, RF energy, or the like. Energy harvesting may provide a small amount of energy for low-energy devices. Even though energy harvesting may not provide enough energy to charge a battery of power hungry devices, energy harvesting may provide energy for low power or zero power devices, such as IoT devices. An energy harvesting UE may receive a signal from a base station or other UEs.

FIG. 4 is a diagram 400 illustrating example energy harvesting. Harvesting RF energy may be used for various tasks for a wireless device such as data decoding, data reception, data encoding, data transmission, or the like. Harvesting RF energy may allow a UE to perform some tasks, such as data decoding, operating some filters, data encoding, transmitting or receiving data, using the harvested energy. Within a network, a node in the network may interact with other nodes in the network using the RF energy harvested via communications within the network. As illustrated in example 410 of FIG. 4 , an energy harvester 412 at a device may be separate from the information receiver 414 at the device while both the energy harvester 412 and the information receiver 414 may be connected to the antenna 416. Such an architecture may be referred to as a separated receiver architecture. As illustrated in example 420 of FIG. 4 , an energy harvester 422 at a device and an information receiver 424 may be connected to the antenna 426 via a time switcher 428. Such an architecture may be referred to as a time switching architecture. As illustrated in example 430 of FIG. 4 , an energy harvester 432 at a device and an information receiver 434 at the device may be connected to the antenna 436 via a power splitter 438. Such an architecture may be referred to as a power splitting architecture.

FIG. 5 is a diagram 500 illustrating example time switching architecture for energy harvesting. The time switching architecture may allow the device to switch between the information receiver 504 or the RF energy harvester 502. As an example, the energy harvested at receiver j from source i may be calculated as follows: E_(j)=ηP_(i)|g_(i-j)|² αT. The parameter α may be 0≤α≤1 and may be a fraction of time allocated for energy harvesting. The parameter T may denote time. The parameter η may denote an efficiency associated with the energy harvesting. The parameter P_(i) may denote a transmit power at source i. The parameter g_(i-j) may denote a channel gain between source i and receiver j. In some aspects, a data rate R_(i-j) may be

${\left( {1 - \alpha} \right){\log_{2}\left( {1 + \frac{{❘g_{i - j}❘}^{2}P_{i}}{\kappa W}} \right)}},$

where κ and W may denote the noise spectral density and a channel bandwidth.

FIG. 6 is a diagram 600 illustrating example power splitting architecture for energy harvesting. The power splitting architecture may allow a received RF signal to be split into two streams, one stream for information decoding by the information decoder 604 and the other stream for energy harvesting by the energy harvester 602. In some aspects, the energy harvested at receiver j from source i may be calculated as E_(j)=ηρP_(i)|g_(i-j)|². The parameter ρ may denote fraction of power allocated for energy harvesting by the power splitter and 0≤ρ≤1. The parameter η may denote an efficiency associated with the energy harvesting. The parameter P_(i) may denote a transmit power at source i. The parameter g_(i-j) may denote a channel gain between source i and receiver j. In some aspects, a data rate R_(i-j) may be

${\log_{2}\left( {1 + \frac{{❘g_{i - j}❘}^{2}\left( {1 - \rho} \right)P_{i}}{\kappa W}} \right)},$

where κ and W may denote the noise spectral density and a channel bandwidth.

Example aspects provided herein provide signaling mechanisms to facilitate operations of one or more charging UEs and IoT devices to more efficiently determine various charging related parameters, such as the charging rate, which UE to charge and which UEs to be charged and under what conditions the charging may be triggered. Some example aspects provided herein may use reinforcement learning, Q-learning, distributed optimization solution, or the like to determine the charging behavior of a network with multiple IoT devices that may use charging.

FIG. 7 is a diagram 700 illustrating an example communication flow between an IoT device 702 (which may be a UE) and a charging UE 704 (which may also be a IoT device). As illustrated in FIG. 7 , the IoT device 702 may transmit a charging request 706 to the charging UE 704. Upon receiving the charging request 706 from the IoT device 702, the charging UE 704 may transmit a fulfillment or a denial 708 to the IoT device 702 to fulfill the charging request 706 or deny the charging request 706. In some aspects, upon transmitting the charging request 706 or receiving fulfillment or denial of the charging request 706, the IoT device 702 may broadcast information 710 about one or more charging requests, including the charging request 706. In some aspects, the information 710 may include one or more of: 1) whether or not the charging request was fulfilled, 2) the average time it took the charging request to be fulfilled, 3) the urgency level of the charging request, 4) charging rate requested and charging rate received, or 5) whether an alternative charging source such as a solar energy was available or not. In some aspects, the IoT device 702 may transmit the information 710 every M requests, where M may be a RRC configured positive integer. For example, the IoT device may transmit one or more additional charging requests 706N and receive one or more fulfilment or approval 708N before broadcasting the information 710.

In some aspects, a Markov decision process may be defined. A Markov decision process may be a discrete-time stochastic control process and may provide a mathematical framework for modeling decision making in situations where outcomes are partly random and partly under control. In a Markov decision process, S may denote a set of states called the state space and A may denote a set of actions called the action space. After taking an action A, state S may enter transitions which may be denoted by P(S′|S,A) where S′ is a new state, S is the current state, and A is the current taken action. The rewards of the action may be rewards R(S,A,S′) (and discount γ). Discount γ may represent a discount factor that decreases the reward. In a Markov decision process, a finite number of states and actions may be assumed. In Markov decision process, at each time the agent (e.g., the IoT device 702/the UE 704) observes a state and an action, the incurred rewards may be maximized. The reward and the successor state may depend on the current state and the chosen action. Successor generations may be probabilistic, based on the uncertainty regarding the environment in which the search takes place. For example, an action might sometimes fail to result in the desired target state, instead staying in the current state with a small probability.

In some aspects, a state may be defined as the number of UE/IoT devices requesting energy charge, the available power at the charging UEs, or time since last request per UE/IoT device or average time of the last request of each UE/IoT device. The actions of the Markov decision process may be defined as charging UE x (e.g., UE 704) charges IoT device y (e.g., IoT device 702) with probability p(x,y). Therefore, device x may have the option to charge device y without a request and the optimization problem of the Markov decision process may converge to optimal via learning.

In some aspects, upon receiving the information 710 broadcasted, each charging UE including the charging UE 704 may update its charging probability based on the information 710 (which may be the reward and may be feedback) at 712.

FIG. 8 is a flowchart 800 of a method of wireless communication. The method may be performed by an IoT device (e.g., the UE 104, the IoT device 702; the apparatus 1002).

At 802, the IoT device may transmit, to a UE, a charging request to charge the IoT device. For example, the IoT device 702 may transmit, to a UE 704, a charging request 706 to charge the IoT device 702. In some aspects, 802 may be performed by charging component 1042 in FIG. 10 . In some aspects, the UE may be an energy harvesting UE.

At 804, the IoT device may receive, from the UE, a fulfillment or a denial associated with the charging request. For example, the IoT device 702 may receive, from the UE 704, a fulfillment or a denial 708 associated with the charging request 706. In some aspects, 804 may be performed by charging component 1042 in FIG. 10 .

At 806, the IoT device may broadcast information related to the charging request after receiving the fulfillment or the denial associated with the charging request. For example, the IoT device 702 may broadcast information 710 related to the charging request 706 after receiving the fulfillment or the denial 708 associated with the charging request 706. In some aspects, 806 may be performed by charging component 1042 in FIG. 10 . In some aspects, the information may include an indication of the fulfillment or the denial. In some aspects, the information may include an average time associated with fulfilling one or more charging requests including the charging request. In some aspects, the information may include an indication of an alternative charging source associated with the IoT device. In some aspects, the alternative charging source may include solar energy. In some aspects, the IoT device may broadcast the information related to the charging request per M charging requests including the charging request, where M is a positive integer configured via RRC signaling.

FIG. 9 is a flowchart 900 of a method of wireless communication. The method may be performed by a UE (e.g., the UE 104, the UE 704; the apparatus 1102).

At 902, the UE may receive, from an IoT device, a charging request to charge the IoT device. For example, the UE 704 may receive, from an IoT device 702, a charging request 706 to charge the IoT device 702. In some aspects, 902 may be performed by charging component 1142 in FIG. 11 . In some aspects, the UE may be an energy harvesting UE.

At 904, the UE may transmit, to the IoT device, a fulfillment or a denial associated with the charging request. For example, the UE 704 may transmit, to the IoT device 702, a fulfillment or a denial 708 associated with the charging request 706. In some aspects, 904 may be performed by charging component 1142 in FIG. 11 .

At 906, the UE may receive, from the IoT device, a broadcast including information related to the charging request after transmitting the fulfillment or the denial associated with the charging request. For example, the UE 704 may receive, from the IoT device 702, a broadcast including information 710 related to the charging request 706 after transmitting the fulfillment or the denial 708 associated with the charging request 706. In some aspects, 906 may be performed by charging component 1142 in FIG. 11 . In some aspects, the information may include an indication of the fulfillment or the denial. In some aspects, the information may include an average time associated with fulfilling one or more charging requests including the charging request. In some aspects, the information may include an indication of an alternative charging source associated with the IoT device. In some aspects, the alternative charging source may include solar energy. In some aspects, the IoT device may broadcast the information related to the charging request per M charging requests including the charging request, where M is a positive integer configured via RRC signaling.

In some aspects, the UE may compute a Markov decision process including one or more states and one or more actions. In some aspects, the one or more states may be defined based on a number of one or more devices requesting an energy charge including the IoT device, one or more available powers at one or more UEs including the UE, and a time since a last charging request per each device of the one or more devices or an average time of the last charging request per each device of the one or more devices.

FIG. 10 is a diagram 1000 illustrating an example of a hardware implementation for an apparatus 1002. The apparatus 1002 may be a IoT device, a component of a IoT device, or may implement IoT device functionality. In some aspects, the apparatus 1002 may include a baseband unit 1004. The baseband unit 1004 may communicate through a cellular RF transceiver 1022 with the UE 104. The baseband unit 1004 may include a computer-readable medium/memory. The baseband unit 1004 is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the baseband unit 1004, causes the baseband unit 1004 to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the baseband unit 1004 when executing software. The baseband unit 1004 further includes a reception component 1030, a communication manager 1032, and a transmission component 1034. The communication manager 1032 includes the one or more illustrated components. The components within the communication manager 1032 may be stored in the computer-readable medium/memory and/or configured as hardware within the baseband unit 1004. The baseband unit 1004 may be a component of the base station 310 and may include the memory 376 and/or at least one of the TX processor 316, the RX processor 370, and the controller/processor 375.

The communication manager 1032 may include a charging component 1042 that may transmit, to a UE, a charging request to charge the IoT device, receive, from the UE, a fulfillment or a denial associated with the charging request, or broadcast information related to the charging request after receiving the fulfillment or the denial associated with the charging request, e.g., as described in connection with 802, 804, or 806 of FIG. 8 .

The apparatus may include additional components that perform each of the blocks of the algorithm in the flowchart of FIG. 8 . As such, each block in the flowcharts of FIG. 8 may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

As shown, the apparatus 1002 may include a variety of components configured for various functions. In one configuration, the apparatus 1002, and in particular the baseband unit 1004, may include means for transmitting, to a UE, a charging request to charge the IoT device. The baseband unit 1004 may further include means for receiving, from the UE, a fulfillment or a denial associated with the charging request. The baseband unit 1004 may further include means for broadcasting information related to the charging request after receiving the fulfillment or the denial associated with the charging request. The baseband unit 1004 may further include means for broadcasting the information related to the charging request per M charging requests including the charging request. The means may be one or more of the components of the apparatus 1002 configured to perform the functions recited by the means. As described supra, the apparatus 1002 may include the TX Processor 316, the RX Processor 370, and the controller/processor 375. As such, in one configuration, the means may be the TX Processor 316, the RX Processor 370, and the controller/processor 375 configured to perform the functions recited by the means.

FIG. 11 is a diagram 1100 illustrating an example of a hardware implementation for an apparatus 1102. The apparatus 1102 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1002 may include a baseband unit 1104. The baseband unit 1104 may communicate through a cellular RF transceiver 1122 with the UE 104. The baseband unit 1104 may include a computer-readable medium/memory. The baseband unit 1104 is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the baseband unit 1104, causes the baseband unit 1104 to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the baseband unit 1104 when executing software. The baseband unit 1104 further includes a reception component 1130, a communication manager 1132, and a transmission component 1134. The communication manager 1132 includes the one or more illustrated components. The components within the communication manager 1132 may be stored in the computer-readable medium/memory and/or configured as hardware within the baseband unit 1104. The baseband unit 1104 may be a component of the base station 310 and may include the memory 376 and/or at least one of the TX processor 316, the RX processor 370, and the controller/processor 375.

The communication manager 1132 may include a charging component 1142 that may receive, from an IoT device, a charging request to charge the IoT device, transmit, to the IoT device, a fulfillment or a denial associated with the charging request, or receive, from the IoT device, a broadcast including information related to the charging request after transmitting the fulfillment or the denial associated with the charging request, e.g., as described in connection with 902, 904, or 906 of FIG. 9 .

The apparatus may include additional components that perform each of the blocks of the algorithm in the flowchart of FIG. 9 . As such, each block in the flowchart of FIG. 9 may be performed by a component and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by a processor configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by a processor, or some combination thereof.

As shown, the apparatus 1102 may include a variety of components configured for various functions. In one configuration, the apparatus 1102, and in particular the baseband unit 1104, may include means for receiving, from an IoT device, a charging request to charge the IoT device. The baseband unit 1104 may further include means for transmitting, to the IoT device, a fulfillment or a denial associated with the charging request. The baseband unit 1104 may further include means for receiving, from the IoT device, a broadcast including information related to the charging request after transmitting the fulfillment or the denial associated with the charging request. The baseband unit 1104 may further include means for computing a Markov decision process including one or more states and one or more actions. The means may be one or more of the components of the apparatus 1102 configured to perform the functions recited by the means. As described supra, the apparatus 1102 may include the TX Processor 316, the RX Processor 370, and the controller/processor 375. As such, in one configuration, the means may be the TX Processor 316, the RX Processor 370, and the controller/processor 375 configured to perform the functions recited by the means.

It is understood that the specific order or hierarchy of blocks in the processes/flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes/flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Terms such as “if,” “when,” and “while” should be interpreted to mean “under the condition that” rather than imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.”

The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.

Aspect 1 is an apparatus for wireless communication at an IoT device, comprising: a memory; and at least one processor coupled to the memory and configured to: transmit, to a UE, a charging request to charge the IoT device; receive, from the UE, a fulfillment or a denial associated with the charging request; and broadcast information related to the charging request after receiving the fulfillment or the denial associated with the charging request.

Aspect 2 is the apparatus of aspect 1, wherein the information comprises an indication of the fulfillment or the denial.

Aspect 3 is the apparatus of any of aspects 1-2, wherein the information comprises an average time associated with fulfilling one or more charging requests including the charging request.

Aspect 4 is the apparatus of any of aspects 1-3, wherein the information comprises an urgency level associated with the charging request.

Aspect 5 is the apparatus of any of aspects 1-4, wherein the information comprises an indication of an alternative charging source associated with the IoT device.

Aspect 6 is the apparatus of any of aspects 1-5, wherein the alternative charging source comprises solar energy.

Aspect 7 is the apparatus of any of aspects 1-6, wherein the at least one processor coupled to the memory is further configured to: broadcast the information related to the charging request per M charging requests comprising the charging request, wherein M is a positive integer configured RRC signaling.

Aspect 8 is the apparatus of any of aspects 1-7, wherein the UE is an energy harvesting UE.

Aspect 9 is the apparatus of any of aspects 1-8, further comprising a transceiver coupled to the at least one processor.

Aspect 10 is an apparatus for wireless communication at a UE, comprising: a memory; and at least one processor coupled to the memory and configured to: receive, from an IoT device, a charging request to charge the IoT device; transmit, to the IoT device, a fulfillment or a denial associated with the charging request; and receive, from the IoT device, a broadcast including information related to the charging request after transmitting the fulfillment or the denial associated with the charging request.

Aspect 11 is the apparatus of aspect 10, wherein the information comprises an indication of the fulfillment or the denial.

Aspect 12 is the apparatus of any of aspects 10-11, wherein the information comprises an average time associated with fulfilling one or more charging requests including the charging request.

Aspect 13 is the apparatus of any of aspects 10-12, wherein the information comprises an urgency level associated with the charging request.

Aspect 14 is the apparatus of any of aspects 10-13, wherein the information comprises an indication of an alternative charging source associated with the IoT device.

Aspect 15 is the apparatus of any of aspects 10-14, wherein the alternative charging source comprises solar energy.

Aspect 16 is the apparatus of any of aspects 10-15, wherein the UE is an energy harvesting UE.

Aspect 17 is the apparatus of any of aspects 10-16, further comprising a transceiver coupled to the at least one processor.

Aspect 18 is the apparatus of any of aspects 10-17, wherein the at least one processor coupled to the memory is further configured to: compute a Markov decision process comprising one or more states and one or more actions, wherein the one or more states are defined based on a number of one or more devices requesting an energy charge including the IoT device, one or more available powers at one or more UEs including the UE, and a time since a last charging request per each device of the one or more devices or an average time of the last charging request per each device of the one or more devices.

Aspect 19 is the apparatus of any of aspects 10-18, wherein the one or more actions are defined based on a probability of charging associated with each UE of the one or more UEs and each device of the one or more devices.

Aspect 20 is the apparatus of any of aspects 10-19, further comprising a transceiver coupled to the at least one processor.

Aspect 21 is a method of wireless communication for implementing any of aspects 1 to 9.

Aspect 22 is an apparatus for wireless communication including means for implementing any of aspects 1 to 9.

Aspect 23 is a computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 1 to 9.

Aspect 24 is a method of wireless communication for implementing any of aspects 10 to 20.

Aspect 25 is an apparatus for wireless communication including means for implementing any of aspects 10 to 20.

Aspect 26 is a computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 10 to 20. 

1. An apparatus for wireless communication at an Internet of Things (IoT) device, comprising: at least one antenna; a memory; and at least one processor coupled to the memory and configured to: harvest energy via a first radio frequency (RF) signal received via the at least one antenna; wirelessly transmit, to a first user equipment (UE) via the at least one antenna, a second RF signal comprising a first charging request to charge the IoT device; receive, from the first UE via the at least one antenna, a third RF signal comprising a fulfillment or a denial associated with the first charging request; broadcast, for at least the first UE and a second UE via the at least one antenna after receiving the fulfillment or the denial associated with the first charging request, a fourth RF signal comprising information related to the first charging request and the fulfillment or the denial; and receive, based on the information, a fifth RF signal, via the at least one antenna, configured to charge the IoT device without transmission of a second charging request to charge the IoT device.
 2. The apparatus of claim 1, wherein the information comprises an indication of the fulfillment or the denial.
 3. The apparatus of claim 1, wherein the information comprises an average time associated with fulfilling one or more charging requests including the first charging request.
 4. The apparatus of claim 1, wherein the information comprises an urgency level associated with the first charging request.
 5. The apparatus of claim 1, wherein the information comprises an indication of an alternative charging source associated with the IoT device.
 6. The apparatus of claim 5, wherein the alternative charging source comprises solar energy.
 7. The apparatus of claim 1, wherein the at least one processor coupled to the memory is further configured to: broadcast the information related to the first charging request per M charging requests comprising the first charging request, wherein M is a positive integer configured via radio resource control (RRC) signaling.
 8. The apparatus of claim 1, wherein the IoT device is a UE.
 9. The apparatus of claim 1, further comprising a transceiver coupled to the at least one processor and the at least one antenna.
 10. An apparatus for wireless communication at a user equipment (UE), comprising: a memory; and at least one processor coupled to the memory and configured to: wirelessly receive, from an Internet of Things (IoT) device, a first radio frequency (RF) signal comprising a first charging request to charge the IoT device; transmit, to the IoT device, a second RF signal comprising a fulfillment or a denial associated with the first charging request; receive, from the IoT device after transmission of the fulfillment or the denial associated with the first charging request, a third RF signal comprising information related to the first charging request and the fulfillment or the denial; determine, based on the information, an instance to transmit, to the IoT device, a fourth RF signal configured to charge the IoT device without receiving a second charging request from the IoT device; and transmit the fourth RF signal to the IoT device at the instance.
 11. The apparatus of claim 10, wherein the information comprises an indication of the fulfillment or the denial.
 12. The apparatus of claim 10, wherein the information comprises an average time associated with fulfilling one or more charging requests including the first charging request.
 13. The apparatus of claim 10, wherein the information comprises an urgency level associated with the first charging request.
 14. The apparatus of claim 10, wherein the information comprises an indication of an alternative charging source associated with the IoT device.
 15. The apparatus of claim 14, wherein the alternative charging source comprises solar energy.
 16. The apparatus of claim 10, wherein the UE is an energy harvesting UE.
 17. The apparatus of claim 10, further comprising a transceiver coupled to the at least one processor.
 18. The apparatus of claim 10, wherein the at least one processor coupled to the memory is further configured to: compute a Markov decision process comprising one or more states and one or more actions, wherein the one or more states are defined based on a number of one or more devices requesting an energy charge including the IoT device, one or more available powers at one or more UEs including the UE, and a time since a last charging request per each device of the one or more devices or an average time of the last charging request per each device of the one or more devices.
 19. The apparatus of claim 18, wherein the one or more actions are defined based on a respective probability of charging associated with each UE of the one or more UEs and each device of the one or more devices.
 20. (canceled)
 21. A method for wireless communication at an Internet of Things (IoT) device, comprising: harvesting energy via a first radio frequency (RF) signal received via an at least one antenna of the IoT device; wirelessly transmitting, to a first user equipment (UE) via the at least one antenna, a second RF signal comprising a first charging request to charge the IoT device; receiving, from the first UE via the at least one antenna, a fulfillment or a denial associated with the first charging request; broadcasting, for at least the first UE and a second UE via the at least one antenna after receiving the fulfillment or the denial associated with the first charging request, a fourth RF signal comprising information related to the first charging request and the fulfillment or the denial; and receive, based on the information, a fifth RF signal, via the at least one antenna, configured to charge the IoT device without transmission of a second charging request to charge the IoT device.
 22. The method of claim 21, wherein the information comprises an indication of the fulfillment or the denial.
 23. The method of claim 21, wherein the information comprises an average time associated with fulfilling one or more charging requests including the first charging request.
 24. The method of claim 21, wherein the information comprises an urgency level associated with the first charging request.
 25. The method of claim 21, wherein the information comprises an indication of an alternative charging source associated with the IoT device.
 26. The method of claim 25, wherein the alternative charging source comprises solar energy.
 27. The method of claim 21, further comprising: broadcasting the information related to the first charging request per M charging requests comprising the first charging request, wherein M is a positive integer configured via radio resource control (RRC) signaling.
 28. The method of claim 21, wherein the IoT device is a UE.
 29. A method for wireless communication at a user equipment (UE), comprising: wirelessly receiving, from an Internet of Things (IoT) device, a first radio frequency (RF) signal comprising a first charging request to charge the IoT device; transmitting, to the IoT device, a second RF signal comprising a fulfillment or a denial associated with the first charging request; receiving, from the IoT device after transmitting the fulfillment or the denial associated with the first charging request, a third RF signal comprising information related to the first charging request and the fulfillment or the denial; determine, based on the information, an instance to transmit, to the IoT device, a fourth RF signal configured to charge the IoT device without receiving a second charging request from the IoT device; and transmit the fourth RF signal to the IoT device at the instance.
 30. The method of claim 29, wherein the information comprises an indication of the fulfillment or the denial. 